home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 3
/
Cream of the Crop 3.iso
/
comm
/
zoomhint.zip
/
COMIT.A
< prev
next >
Wrap
Text File
|
1992-01-02
|
8KB
|
129 lines
Comit for Windows
IMPORTANT NOTE:
If you are using Windows 3.1, we strongly suggest you run the program
"MSD" (switch to the Windows directory and from the DOS prompt type "MSD")
prior to installing or running your modem. Problems encountered using
modems are most often related to conflicts of ports, speed, and IRQs. MSD
will help you locate these problems and assist in the installation of your
modem and COMit. If you experience problems under Windows 3.0 because of
port or speed conflicts, you may want to consider upgrading to Windows
version 3.1.
NOTICE: If you are using Dashboard, or another replacement for Windows 3.1
Program manager, it may be necessary to install COMit from the Program
manager.
If your modem supports the Rockwell V.42 (Software) Driver... Zoom - AFC /
AFX / AMC / AMX / Pkt2400 then
If you did not set the following when installing COMit, you should...
1) Select "Port" from the settings menu and enable the V.42
settings. There are three: Enable V.42, Error Correction, and Data
Compression.
2) Select "Modems" from the setting menu and select the first modem
in the list "1-Modems supporting V.42"
3) Now, push the test button. If you have set up COMit correctly,
you will get an "OK" message.
Do not select the V.42 Softdriver (RPI) if your modem supports MNP and
V.42bis in hardware. ie: Zoom V-series modems.
Common Problems
Data Communications is a very inexact field and is prone to an
inordinate number of problems. By alleviating some of the common problems
reported with COMit we hope to make your lives a bit easier.
Modem does not work when port speed is set to 14400 - This is probably
the most common problem reported. And the answer is simple, at least from
the COMit standpoint. Do not set your port speed to 14400. It turns out
that most modems, including those 14400 modems, do not support 14400. If
you have a 16550 UART then you need to set your port speed to 38400. In
Windows the standard COM driver does not work well above 38400 and Receive
Overruns will occur. If you do not have a 16550 UART or do not know what
you have then set your port speed to 19200. You can use the Microsoft
utility MSD.EXE included with your Windows system to determine the type of
UART you have. The common ones are 8250, 16450, or 16550 so look for these
numbers under the COM port section.
Receive Overruns are Occurring - This is the next most common problem
that is reported. This is not as easy as the previous problem. The first
thing is to read the previous problem on port speed settings.
If you have this set correctly the next most likely culprit is FLOW
CONTROL. Flow control is set in the COM Driver and Flow Control is also set
in the Modem. The Flow Control in the COM Driver is easy and we set that
for you. But the Flow Control in the Modem is a lot more difficult because
it turns out that there are numerous modems which implement the Flow
Control command differently. Which means if your modem is not in the list
then the chances are that your modem selection is not correct. When this
occurs you can experiment with a different modem until you find one that
works.
You should be using Flow Control for all DATA communications over 2400
BPS or if you have V42 or MNP enabled in a slower modem. And it should be
Hardware Flow Control (In our case RTS/CTS).
Certain Modems do not handle the speed we initialize them at
effectively. They have a tendency to drop off commands at the end of the
Command string (Usually the flow control setting). To overcome this problem
we have a parameter called XMIT Delay in the Settings/Modem Dialog Box.
Place a value of 1 in this box and the initialization and command sequence
will slow down enough to satisfy your modem.
And one last instance occurs when you are dialing into COMit Host Mode
or AutoAnswer Mode with a modem which does not have a V42 or MNP
capabilities and the dialing modem is setup for V42 or MNP. The V42 and
MNP sequences are actually data that is transmitted after a carrier/Connect
sequence has take place. To a modem which does not support V42 or MNP this
data looks like garbage and may result in Receive overruns or some other
odd messages. The best thing to do in this situation is have the party
dialing into COMit disable the MNP or V42 support for the duration of the
call. Usually the negotiation of the V42 and MNP lasts about 1-3 seconds
immediately after the first connect/carrier message.
VT100 Keyboard does not set Home, PGUP, Up Arrow, Etc Keys - The
normal state for the control keys such as HOME, Up Arrow, Page UP, etc is
to manipulate the screen buffer. If you desire to transmit the seqeunces to
the service you are connected to you must toggle the "Scroll Lock key to
the ON postion.
Screen Paints are Choppy - If you are comparing to DOS programs you
will find the screen paints are slower and choppier with slower
MicroComputers. This is because the Graphical Interface is much slower and
has a more difficult time handling the Scrolling process without playing
tricks in the repaint routines.
Screen Paints are aligned incorrectly - This is usually the result of
the Terminal Number of Rows are out of Sync with the number of Rows on the
service that you are using. If the number of rows on the BBS service you
are using are set to 25 then make sure the setting in the Settings/Terminal
Dialog Box is also 25. Usually there is a menu item on the service you are
using for your settings or parameters.
Modem Initialization Error - This error is usually the result of an
mismatch in our modem string and the Modem you are using. You can try
selecting another modem in the list and experimenting with this. Also if
you have added any modem init strings to the settings/Modem Dialog Box take
them out.
ANSI Graphic Characters are not displayed Properly - If those special
characters used on BBS's are not displaying properly this is usually a
result of the FONT selection. The only Font distributed with Windows that
supports these characters is the Terminal FONT. Therefore if you select any
other standard Windows Font you will not see these nice menus and pictures.
Please note that the Terminal Font is not a True Type Font so if you have
the True Type only enabled in the Window Control Panel Font Selection then
you will not see the Terminal Font.
Also note that only Fixed Space fonts are supported for efficiency. To
properly space Proportional Fonts (Which most fonts unfortunately are) it
becomes inefficient in a Windows Communications Environment.
ERRATIC RESPONSE TO COMMANDS
Erratic response to AT commands can be attributed to two things: IRQ
conflicts and/or COM port overlaps.
by Tradewind